Conversion of a presentation to darwin information typing architecture (dita)

ABSTRACT

One embodiment of the present invention discloses a method, computer program product, and system for converting a Microsoft® PowerPoint® file to Darwin Information Typing Architecture (DITA). A document converter receiving a command from a client device to convert one or more PowerPoint slides to DITA, wherein the PowerPoint has been formatted for conversion to DITA. Starting with the first PowerPoint slide, metadata tags, PowerPoint slide and notes text, and file names of grouped images are compiled into a string parsed with DITA markup. If the next slide does not begin a new topic, then that slide&#39;s metadata tags, PowerPoint slide and notes text, and grouped image file names are compiled into a string parsed with DITA markup and appended to the previous slides string. If the next slide begins a new topic, then the string is exported to a DITA topic. This process is repeated throughout the PowerPoint presentation.

FIELD OF THE INVENTION

The present invention relates generally to the field of documentconversion software and more particularly to converting a Microsoft®PowerPoint® file to Darwin Information Typing Architecture (DITA).

BACKGROUND OF THE INVENTION

PowerPoint® is a file format of presentation software created byMicrosoft®. A PowerPoint presentation consists of a number of individualpages or “slides” which are populated with information. The slides maycontain text, notes, graphics and images, movies, sound, or otherobjects.

The Darwin Information Typing Architecture (DITA) is a standardExtensible Markup Language (XML) data model which is used for authoringand publishing content. DITA content is created by dividing informationinto topic items. There are three basic topic types: Task, Concept, andReference. The topics are organized with a title element, elements ofmetadata, and a body element which is comprised of information relatingto the specific topic. The metadata in DITA includes information andattributes about the topic which makes it easier to locate.

SUMMARY

One embodiment of the present invention discloses a method, computerprogram product, and system for converting a Microsoft® PowerPoint® fileto Darwin Information Typing Architecture (DITA). A document converterreceiving a command from a client device to convert one or morePowerPoint slides to DITA, wherein the PowerPoint has been formatted forconversion to DITA. Starting with the first PowerPoint slide, metadatatags, PowerPoint slide and notes text, and file names of grouped imagesare compiled into a string parsed with DITA markup. If the next slidedoes not begin a new topic, then that slide's metadata tags, PowerPointslide and notes text, and grouped image file names are compiled into astring parsed with DITA markup and appended to the previous slidesstring. If the next slide begins a new topic, then the string isexported to a DITA topic. This process is repeated throughout thePowerPoint presentation.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a pictorial representation of a distributed data processingenvironment in accordance with an embodiment of the present invention.

FIG. 2 is a flowchart depicting operational steps of a program forformatting a Microsoft PowerPoint presentation so that it may beconverted to a DITA document in accordance with an embodiment of thepresent invention.

FIG. 3 illustrates operational steps of a program for the automatedconversion of a Microsoft PowerPoint presentation to a DITA document, inaccordance with an embodiment of the present invention.

FIG. 4 depicts a slide information gathering sample algorithm inaccordance with an embodiment of the automated conversion program fromFIG. 3.

FIG. 5 depicts a new topic identification sample algorithm in accordancewith an embodiment of the automated conversion program.

FIG. 6 depicts a block diagram of components of the server computer 108executing the PowerPoint formatting program and automated conversionprogram, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer-readablemedium(s) having computer readable program code/instructions embodiedthereon.

Any combination of one or more computer-readable medium(s) may beutilized. The computer-readable medium may be a computer-readable signalmedium or a computer-readable storage medium. A computer-readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer-readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer-readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer-readable signal medium may include a propagated data signalwith computer-readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer-readable signal medium may be any computer-readable medium thatis not a computer-readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java®, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on a user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable medium that can direct a computer, other programmabledata processing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer-readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram illustrating a dataprocessing environment 100 in accordance with one embodiment of thepresent invention.

Data processing environment 100 includes a client device 102, a storagedevice 106, and a server computer 108 which are connected through anetwork 104. Client device 102 may be a workstation, personal computer,personal digital assistant, mobile phone, or other devices capable ofexecuting program instructions. A user interface 110 is located onclient device 102 and may exist in the form of operating systemsoftware, which may be Windows®, LINUX®, or other systems that includeapplication software such as internet applications and web browsers. Inan embodiment, user interface 110 includes applications which utilizenetwork 104 to access content on storage device 106 or server computer108.

In an embodiment, data processing environment 100 includes network 104,which provides communication between devices such as, but not limited toclient device 102, storage device 106, and server computer 108. Network104 may include connections such as wiring, wireless communication link,fiber optic cables, and other forms of communication. Network 104 mayallow elements of data processing environment 100 to access contentthrough a plurality of methods, including the internet, an intranetconnection, telecommunications service provider, local area connection,and others.

Storage device 106 may represent any type of storage which is capable ofstoring data which may be accessed and utilized by client device 102 andserver computer 108, including a database server, a hard drive on acomputing device, flash memory, an external storage device, or othermeans of data storage. As depicted, storage device 106 is a networkedstorage device accessible via network 104. In an alternative embodiment,storage device 106 may be located on client device 102 as a component ofclient device 102. In an example, storage device 106 may be a repositoryfor product information and product instructions which may be accessedby documentation developers and training developers. In another example,storage device 106 may be a repository database consisting of contentsuch as Microsoft PowerPoint presentations, and Darwin InformationTyping Architecture (DITA) documents which may be accessed by clientdevice 102 and server computer 108.

A document converter program 112 is located on server computer 108 andcan access and convert content located on storage device 106 responsiveto a command from client device 102. In an embodiment, documentconverter program 112 can convert Microsoft PowerPoint presentationsinto DITA documents. In the depicted embodiment, document converterprogram 112 is located on server computer 108 in the form of anapplication. In another embodiment, document converter program 112 maybe located on client device 102. Server computer 108 may be anyprogrammable electronic device as described previously with respect toclient device 102. In one embodiment, server computer 108 represents a“cloud” of computers interconnected by one or more networks, whereserver computer 108 is a primary server for a computer system utilizingclustered computers and components to act as a single pool of seamlessresources when accessed through network 104. For example, thisimplementation may be preferred for data centers and for cloud computingapplications

Embodiments of the present invention recognize that documentationdevelopers who produce product support information and trainingdevelopers who produce end user training documents often end upduplicating each others work. Since both are writing for an end useraudience, a common repository for product information and productinstructions could reduce the duplication of documentation. However, toutilize each others information in such a repository effectively, acommon file format should be used.

The Darwin Information Typing Architecture (DITA) supports a singlesourcing of content. DITA has been widely used by documentation teams,however it is not widely used on training development teams. A largevolume of current training content exists in the form of MicrosoftPowerPoint presentations rather than DITA. This means that a largeamount of training content exists in a format different than a widelyused format for the product support documentation. A means to convertMicrosoft PowerPoint presentations to DITA documents would allowtraining documents to be converted into the same format as productsupport documents, which would allow documentation developers andtraining developers to utilize each others information effectively.Document converter program 112 includes a PowerPoint formatting program200 for preparing a Microsoft PowerPoint presentation so that it may beconverted to a DITA document. In one embodiment, document converterprogram 112 also includes an automated conversion program 300 forconverting a Microsoft PowerPoint presentation to a DITA document. Aperson of ordinary skill in the art will recognize that the softwaredescribed herein will be applicable for any type of presentationsoftware. Document converter program 112, PowerPoint formatting program200, and automated conversion program 300 may be stored on servercomputer 108 in the form of program instructions. However, in otherexamples, the programs may be stored on remote storage devices (e.g.,storage device 106), servers, or networked computer systems. Detailedimplementation of programs 200 and 300 are discussed with regard toFIGS. 2 and 3 respectively.

Server computer 108 may include internal and external hardwarecomponents, as depicted and described in further detail with respect toFIG. 6.

FIG. 2 is a flowchart depicting operational steps of PowerPointformatting program 200. In one embodiment, PowerPoint formatting program200 prepares a PowerPoint slide to be converted to a DITA documentresponsive to user specifications.

In step 202, PowerPoint formatting program 200 receives a command fromclient device 102 to add metadata tags to a PowerPoint slide. Thecommand to add metadata tags to a PowerPoint slide may be accomplishedthrough a user input in a user form activated by clicking a button on aPowerPoint add-in toolbar. In step 204, PowerPoint formatting program200 prompts a user to define metadata tags for the PowerPoint slide. Themetadata tags defined in step 204 may be marking the concept, task, andreference topic types which are used in DITA. When the user is promptedto define the metadata tags for the slide, the user may define theappropriate topic title and topic file name for the slide, and thendecide whether the topic is a concept, task, or reference. Responsive tothe user definition from step 204, the PowerPoint slide is tagged withthe appropriate metadata, which prepares the slide for conversionthrough automated conversion program 300. In an embodiment, step 202 mayalso be a command to edit metadata tags which have been previouslydefined by the user.

In step 206, PowerPoint formatting program 200 receives a command togroup images in the PowerPoint slide. In an example, the command togroup the images in a PowerPoint slide comes from a user on clientdevice 102. The selection of images to group in step 206 may beaccomplished by the user selecting the desired component graphicelements on the slide and then selecting the group image command in aPowerPoint add-in toolbar. In an embodiment, the images grouped may begraphical elements of diagrams such as lines, arrows and boxes. Thegrouping of images allows the original arrangement of the images to bepreserved when converting the slide to DITA. Subsequent to the imagesbeing grouped responsive to the user command in step 206, the imagegroup is then ready to be exported as an image file in automatedconversion program 300. In one embodiment, when the images are groupedin step 206, PowerPoint formatting program 200 adds a bottom layer tothe group of images and the group is tagged as a composite image to beexported as a single image file. The addition of the bottom layer to thegroup of images may be used to provide a uniform background to the groupof images which does not obscure any of the elements of the group ofimages. The command to group the images in a PowerPoint slide in step206 may be accomplished through a user input in a PowerPoint add-intoolbar. PowerPoint formatting program 200 tags each group of images forexport as an image file (step 208). In an embodiment, in step 208 eachgroup of images is tagged with metadata that defines the file name forthe image file to be exported/created and flags the group to be exportedto a single image file by the automated conversion program 300. In anexample where a PowerPoint presentation is comprised of more than oneslide, PowerPoint formatting program 200 may be repeated for every slidein the PowerPoint presentation.

FIG. 3 is a flowchart depicting operational steps of automatedconversion program 300. Automated conversion program 300 may beinitiated after PowerPoint formatting program 200 has been completed foreach slide in the PowerPoint. In one embodiment, automated conversionprogram 300 converts a Microsoft PowerPoint presentation to a DITAdocument.

In step 302, automated conversion program 300 receives a command toconvert a PowerPoint file or one or more PowerPoint slides to a DITAdocument. In an example, the command to convert a PowerPoint file toDITA in step 302 may be accomplished through a user input in aPowerPoint add-in toolbar. In step 304, automated conversion program 300compiles the metadata tags, PowerPoint slide text, PowerPoint slidenotes text, and grouped image file names into a string parsed with DITAmarkup for a slide in the PowerPoint file. The metadata tags contain atleast in part a topic title, topic file name, and topic type. In anexample, the image file names compiled in step 304 of automatedconversion program 300 are the grouped image file names which weretagged for export in step 208 of PowerPoint formatting program 200. Anexample of an image file format which the group of images may be savedas is a JPEG image file. In an embodiment, the PowerPoint slide textcompiled in step 304 may be the text in the body of the PowerPoint slideor text in other place holders in the PowerPoint slide. The PowerPointnotes text compiled in step 304 may be the text in the notes section ofthe PowerPoint slide.

In step 306, automated conversion program 300 determines whether thenext slide is the beginning of a new topic. The determination that thenext slide is the beginning of a new topic in step 306 may beaccomplished through accessing metadata tags which were assigned to theslide in step 204 of PowerPoint formatting program 200. If automatedconversion program 300 determines that the next slide does not begin anew topic (no branch of decision block 306), automated conversionprogram 300 compiles the metadata tags, PowerPoint slide text,PowerPoint slide notes text, and grouped image file names for the slideinto a string parsed with DITA markup and appends the information to theprevious slides string (step 308). If automated conversion program 300determines that the next slide is the beginning of a new topic (yesbranch of decision block 306), automated conversion program 300 convertsthe string to a DITA topic of the appropriate topic type (step 310). Theappropriate topic type from step 310 can be defined in step 204 ofPowerPoint formatting program 200.

In step 312, automated conversion program 300 determines whether theslide which was previously converted was the last slide. If automatedconversion program 300 determines that it was not the last slide (nobranch of decision block 312), automated conversion program 300 repeats,starting at step 304 for the new slide. If automated conversion program300 determines that it was the last slide (yes branch of decision block312), then automated conversion program 300 is completed. In anembodiment, step 312 ensures that automated conversion program 300repeats for each slide in a PowerPoint file. An exemplary result ofautomated conversion program 300 may be each slide in a PowerPointpresentation is converted and organized into a DITA topic and formattedso that the file may be opened in a DITA authoring or viewing program.

FIG. 4 depicts a slide information gathering sample algorithm 400 thatgathers and compiles information from a PowerPoint slide in accordancewith an embodiment of automated conversion program 300. In anembodiment, slide information gathering sample algorithm 400 compiles atleast in part metadata tags, PowerPoint slide text, PowerPoint notestext, and grouped image file names.

FIG. 5 depicts a new topic identification sample algorithm 500 thatdetermines whether or not a PowerPoint slide contains the beginning of anew topic in accordance with an embodiment of automated conversionprogram 300.

FIG. 6 depicts a block diagram of components of server computer 108 inaccordance with an illustrative embodiment. It should be appreciatedthat FIG. 6 provides only an illustration of one implementation and doesnot imply any limitations with regard to the environment in whichdifferent embodiments may be implemented. Many modifications to thedepicted environment may be made.

Server computer 108 includes communications fabric 602, which providescommunications between computer processor(s) 604, memory 606, persistentstorage 608, communications unit 610, and input/output (I/O)interface(s) 612.

Memory 606 and persistent storage 608 are examples of computer-readabletangible storage devices and media. Memory 606 may be, for example, oneor more random access memories (RAM) 614, cache memory 616, or any othersuitable volatile or non-volatile storage device.

PowerPoint formatting program 200 and automated conversion program 300are stored in persistent storage 608 for execution by one or more of therespective computer processors 604 via one or more memories of memory606. In the embodiment illustrated in FIG. 6, persistent storage 608includes flash memory. Alternatively, or in addition to flash memory,persistent storage 608 may include a magnetic disk storage device of aninternal hard drive, a solid state drive, a semiconductor storagedevice, read-only memory (ROM), EPROM, or any other computer-readabletangible storage device that is capable of storing program instructionsor digital information.

The media used by persistent storage 608 may also be removable. Forexample, a removable hard drive may be used for persistent storage 608.Other examples include an optical or magnetic disk that is inserted intoa drive for transfer onto another storage device that is also a part ofpersistent storage 608, or other removable storage devices such as athumb drive or smart card.

Communications unit 610, in these examples, provides for communicationswith other data processing systems or devices, including resources ofclient device 102, network 104 and storage device 106. In theseexamples, communications unit 610 includes one or more network interfacecards. Communications unit 610 may provide communications through theuse of either or both physical and wireless communications links.PowerPoint formatting program 200 and automated conversion program 300may be downloaded to persistent storage 608 through communications unit610.

I/O interface(s) 612 allows for input and output of data with otherdevices that may be connected to server computer 108. For example, I/Ointerface 612 may provide a connection to external devices 618 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. I/O interface(s) may also connect to a display 620.

Display 620 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

What is claimed is:
 1. A method for converting a presentation file toDarwin Information Typing Architecture (DITA), the method comprising: acomputer receiving a command to convert one or more presentation slidesto a DITA document, wherein the one or more presentation slides to beconverted have been tagged with metadata corresponding to topic type andgrouped graphical element file names; responsive to receiving thecommand to convert one or more presentation slides to a DITA document,the computer compiling information from the presentation slide, theinformation selected from the group consisting of the metadata tags,text in the presentation slide, text in a notes section of thepresentation slide, and grouped graphical element file names from afirst presentation slide of the one or more presentation slides into astring parsed with DITA markup; the computer accessing the metadata tagsfor a second presentation slide and determining whether the secondpresentation slide is a new topic; the computer determining that thesecond presentation slide is a new topic; and responsive to determiningthat the second presentation slide is a new topic, the computerconverting the string parsed with DITA markup to a DITA topic defined bythe metadata in the presentation slide.
 2. The method of claim 1,further comprising: the computer determining that a third presentationslide is not a new topic; and responsive to the computer determiningthat the third presentation slide is not the beginning of a new topic,the computer compiling metadata tags, text in the presentation slide,text in the notes section of the presentation slide, and groupedgraphical element file names into a string parsed with DITA markup andappending to the string of the first presentation slide.
 3. The methodof claim 1, further comprising: prior to the command to convert one ormore presentation slides to a DITA document, the computer receiving acommand to add metadata tags to a presentation slide; responsive toreceiving the command to add metadata tags to a presentation slide, thecomputer prompting a user to define metadata tags for the presentationslide; and responsive to a user defining metadata tags for thepresentation slide, the computer assigning the defined metadata tags tothe presentation slide, the defined metadata tags comprising at least inpart topic type, topic title and topic file name.
 4. The method of claim1, further comprising: prior to the command to convert one or morepresentation slides to a DITA document, the computer receiving a commandto group graphical elements located on a presentation slide; andresponsive to receiving the command to group graphical elements locatedon the presentation slide, the computer assigning metadata tags to thegrouped graphical elements, the metadata tags comprising at least inpart a file name for the group of graphical elements and an indicationthat the group is to be exported to a single image file.
 5. The methodof claim 1, wherein the computer determining that the secondpresentation slide is a new topic by accessing the topic type, topictitle, and topic file name located in the metadata of the secondpresentation slide.
 6. The method of claim 1, wherein the command toconvert one or more presentation slides to a DITA document is receivedas a user input in a presentation add-in toolbar.
 7. The method of claim1, further comprising: prior to the command to convert one or morepresentation slides to a DITA document, the computer receiving a commandto edit metadata tags corresponding to a presentation slide; responsiveto receiving the command to edit metadata tags corresponding to apresentation slide, the computer prompting a user to define metadatatags for the presentation slide; and responsive to a user definingmetadata tags for the presentation slide, the computer assigning thedefined metadata tags to the presentation slide, the defined metadatatags comprising at least in part topic type, topic title and topic filename.
 8. A computer program product for converting a presentation fileto Darwin Information Typing Architecture (DITA), the computer programproduct comprising: one or more computer-readable tangible storagedevices and program instructions stored on the one or morecomputer-readable tangible storage devices, the program instructionscomprising: program instructions to receive a command to convert one ormore presentation slides to a DITA document, wherein the one or morepresentation slides to be converted have been tagged with metadatacorresponding to topic type and grouped graphical element file names;program instructions responsive to receiving the command to convert oneor more presentation slides to a DITA document, to compile informationfrom the presentation slide, the information selected from the groupconsisting of the metadata tags, text in the presentation slide, text ina notes section of the presentation slide, and grouped graphical elementfile names from a first presentation slide of the one or morepresentation slides into a string parsed with DITA markup; programinstructions to access the metadata tags for a second presentation slideand determining whether the second presentation slide is a new topic;program instructions to determine that the second presentation slide isa new topic; and program instructions responsive to determining that thesecond presentation slide is a new topic, to convert the string parsedwith DITA markup to a DITA topic defined by the metadata in thepresentation slide.
 9. The computer program product of claim 8, furthercomprising program instructions, stored on the one or morecomputer-readable tangible storage devices, to: determine that a thirdpresentation slide is not a new topic; and responsive to determiningthat the third presentation slide is not the beginning of a new topic,compile metadata tags, text in the presentation slide, text in the notessection of the presentation slide, and grouped graphical element filenames into a string parsed with DITA markup and append to the string ofthe second presentation slide.
 10. The computer program product of claim8, further comprising program instructions, stored on the one or morecomputer-readable tangible storage devices, to: prior to the command toconvert one or more presentation slides to a DITA document, receive acommand to add metadata tags to a presentation slide; responsive toreceiving the command to add metadata tags to a presentation slide,prompt a user to define metadata tags for the presentation slide; andresponsive to the user defining metadata tags for the presentationslide, assign the defined metadata tags to the presentation slide, thedefined metadata tags comprising at least in part topic type, topictitle and topic file name.
 11. The computer program product of claim 8,further comprising program instructions, stored on the one or morecomputer-readable tangible storage devices, to: prior to the command toconvert one or more presentation slides to a DITA document, receive acommand to group graphical elements located on a presentation slide; andresponsive to receiving the command to group graphical elements locatedon the presentation slide, assign metadata tags to the grouped graphicalelements, the metadata tags comprising at least in part a file name forthe group of graphical elements and an indication that the group is tobe exported to a single image file.
 12. The computer program product ofclaim 8, wherein the program instructions to determine that the secondpresentation slide is a new topic is based on accessing the topic type,topic title, and topic file name located in the metadata of the secondpresentation slide.
 13. The computer program product of claim 8, whereinthe command to convert one or more presentation slides to a DITAdocument is received as user input in a presentation add-in toolbar. 14.The computer program product of claim 8, further comprising programinstructions, stored on the one or more computer-readable tangiblestorage devices, to: prior to the command to convert one or morepresentation slides to a DITA document, receive a command to editmetadata tags corresponding to a presentation slide; responsive toreceiving the command to edit metadata tags corresponding to apresentation slide, prompt a user to define metadata tags for thepresentation slide; and responsive to the user defining metadata tagsand for the presentation slide, assign the defined metadata tags to thepresentation slide, the defined metadata tags comprising at least inpart topic type, topic title and topic file name.
 15. A computer systemfor converting presentation file to Darwin Information TypingArchitecture (DITA), the computer system comprising: one or morecomputer processors; one or more computer-readable tangible storagedevices; program instructions stored on the one or morecomputer-readable tangible storage devices for execution by at least oneof the one or more processors, the program instructions comprising:program instructions to receive a command to convert one or morepresentation slides to a DITA document, wherein the one or morepresentation slides to be converted have been tagged with metadatacorresponding to topic type and grouped graphical element file names;program instructions responsive to receiving the command to convert oneor more presentation slides to a DITA document, to compile informationfrom the presentation slide, the information selected from the groupconsisting of the metadata tags, text in the presentation slide, text ina notes section of the presentation slide, and grouped graphical elementfile names from a first presentation slide of the one or morepresentation slides into a string parsed with DITA markup; programinstructions to access the metadata tags for a second presentation slideand determining whether the second presentation slide is a new topic;program instructions to determine that the second presentation slide isa new topic; and program instructions responsive to determining that thesecond presentation slide is a new topic, to convert the string parsedwith DITA markup to a DITA topic defined by the metadata in thepresentation slide.
 16. The computer system of claim 15, furthercomprising program instructions, stored on the one or morecomputer-readable tangible storage devices for execution by at least oneof the one or more processors, to: determine that a third presentationslide is not a new topic; and responsive to determining that the thirdpresentation slide is not the beginning of a new topic, compile metadatatags, text in the presentation slide, text in the notes section of thepresentation slide, and grouped graphical element file names into astring parsed with DITA markup and append to the string of the secondpresentation slide.
 17. The computer system of claim 15, furthercomprising program instructions, stored on the one or morecomputer-readable tangible storage devices for execution by at least oneof the one or more processors, to: prior to the command to convert oneor more presentation slides to a DITA document, to receive a command toadd metadata tags to a presentation slide; responsive to receiving thecommand to add metadata tags to a presentation slide, to prompt a userto define metadata tags and for the presentation slide; and responsiveto a user defining metadata tags for the presentation slide, to assignthe defined metadata tags to the presentation slide, the definedmetadata tags comprising at least in part topic type, topic title andtopic file name.
 18. The computer system of claim 15, further comprisingprogram instructions, stored on the one or more computer-readabletangible storage devices for execution by at least one of the one ormore processors, to: prior to the command to convert one or morepresentation slides to a DITA document, to receive a command to groupgraphical elements located on a presentation slide; and responsive toreceiving the command to group graphical elements located on thepresentation slide, to assign tags to the grouped graphical elements,the tags comprising at least in part a file name for the group ofgraphical elements and an indication that the group is to be exported toa single image file.
 19. The computer system of claim 15, wherein theprogram instructions to determine that the second presentation slide isa new topic is based on accessing the topic type, topic title, and topicfile name located in the metadata of the second presentation slide. 20.The computer system of claim 15, wherein the command to convert one ormore presentation slides to a DITA document is received as a user inputin a presentation add-in toolbar.
 21. The computer system of claim 15,further comprising program instructions, stored on the one or morecomputer-readable tangible storage devices for execution by at least oneof the one or more processors, to: prior to the command to convert oneor more presentation slides to a DITA document, to receive a command toedit metadata tags corresponding to a presentation slide; responsive toreceiving the command to edit metadata tags corresponding to apresentation slide, to prompt a user to define metadata tags for thepresentation slide; and responsive to a user defining metadata tags forthe presentation slide, to assign the defined metadata tags to thepresentation slide, the defined metadata tags comprising at least inpart topic type, topic title and topic file name.